Electronic system for authorization and use of cross-linked resource instruments

ABSTRACT

Embodiments of the invention are directed to systems, methods, and computer program products for authorization and use of cross-linked resource instruments. As such, the system results in increased flexibility of resource transfers by enabling a user to establish a virtual link between an account and a resource instrument not originally associated with said account. The user may then complete a transaction using a preferred account, despite the preferred resource instrument being lost, damaged, or otherwise ineffective. Furthermore, the system may activate crosslink requests in real-time, allowing a user to rapidly complete a transaction from any location.

BACKGROUND

A physical resource instrument is susceptible to becoming damaged, lost,or otherwise rendered ineffective. Typically, when this occurs, a usermust use a secondary resource instrument associated with a secondaryentity or source retainer to complete resource transfers. If the userwants to complete a resource transfer using an original source retainerassociated with an original resource instrument which is damaged, lost,or otherwise rendered ineffective, the user must wait for a replacementresource instrument to be issued. As such, a need exists for a user tobe able to associate a secondary resource instrument with the sourceretainer associated with a lost or damaged primary resource instrumentin order to complete a resource transfer.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

Embodiments of the invention relate to systems, methods, and computerprogram products for authorization and use of cross-linked resourceinstruments, the invention including: receiving, from a managing entity,a request for a crosslink, wherein the request comprises informationidentifying a requester, information identifying a resource instrument,information identifying an account associated with the requester and notassociated with the resource instrument, and information indicating atime at which to activate the request; storing the request in acrosslink database; receiving, from the managing entity, transactiondata from a transaction between a user and a third party system, whereinthe transaction data comprises at least information identifying theuser, information identifying the resource instrument used, and atimestamp; identifying, based on the information identifying the user, astored request in the crosslink database wherein the requester matchesthe user identified in the transaction data and the request is activatedduring the time at which the transaction occurred; determining whetherthe resource instrument identified in the stored request matches theresource instrument identified in the transaction data; transmitting,based on determining that the resource instrument identified in thestored request matches the resource instrument identified in thetransaction data, the transaction data to a primary institution systemassociated with the account identified in the stored request; andreceiving, from the primary institution system, a confirmation oftransaction authorization and completion.

In some embodiments, the invention further includes transmitting, to themanaging entity and based on the request for the crosslink being storedin the crosslink database, a notification.

In some embodiments, the request for the crosslink from the managingentity is generated by the managing entity in response to receiving auser request from a user device via a network. In response receiving toa user request from a user device via a network.

In some embodiments, the information indicating the time at which toactivate the request indicates that the request is activatedimmediately.

In some embodiments, the request comprises information indicatinganother time at which to deactivate the request.

In some embodiments, the request for the crosslink further comprisesinformation indicating a secondary account, wherein the secondaryaccount is associated with both the requester and the resourceinstrument identified in the request.

In some embodiments, upon determining whether the resource instrumentidentified in the stored request matches the resource instrumentidentified in the transaction data, the invention further includestransmitting a message comprising the transaction data to a secondaryinstitution system associated with the secondary account identified inthe stored request.

In some embodiments, the message transmitted to the secondaryinstitution system further comprises information identifying the primaryinstitution system and instructions to forward the transaction data tothe primary institution system.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 illustrates an operating environment for the crosslinking system,in accordance with one embodiment of the present disclosure;

FIG. 2 is a block diagram illustrating the crosslinking system;

FIG. 3 is a block diagram illustrating a crosslink request associatedwith the crosslinking system; and

FIG. 4 is a flow diagram illustrating a process using the crosslinkingsystem, in accordance with one embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to elements throughout. Wherepossible, any terms expressed in the singular form herein are meant toalso include the plural form and vice versa, unless explicitly statedotherwise. Also, as used herein, the term “a” and/or “an” shall mean“one or more,” even though the phrase “one or more” is also used herein.

“Entity” or “managing entity” as used herein may refer to anyorganization, entity, or the like in the business of moving, investing,or lending money, dealing in financial instruments, or providingfinancial services. This may include commercial banks, thrifts, federaland state savings banks, savings and loan associations, credit unions,investment companies, insurance companies and the like. In someembodiments, the entity may allow a user to establish a source retaineror an account with the entity. A “source retainer” or an “account” maybe the relationship that the user has with the entity. Examples ofsource retainers or accounts include a deposit account, such as atransactional account (e.g., a banking account), a savings account, aninvestment account, a money market account, a time deposit, a demanddeposit, a pre-paid account, a credit account, or the like. The accountis associated with and/or maintained by the entity. In otherembodiments, an entity may not be a financial institution. In stillother embodiments, the entity may be the merchant itself.

“Entity system” or “managing entity system” as used herein may refer tothe computing systems, devices, software, applications, communicationshardware, and/or other resources used by the entity to perform thefunctions as described herein. Accordingly, the entity system maycomprise desktop computers, laptop computers, servers,Internet-of-Things (“IoT”) devices, networked terminals, mobilesmartphones, smart devices (e.g., smart watches), network connections,and/or other types of computing systems or devices and/or peripheralsalong with their associated applications.

“User” as used herein may refer to an individual associated with anentity. As such, in some embodiments, the user may be an individualhaving past relationships, current relationships or potential futurerelationships with an entity. In some instances, a “user” is anindividual who has a relationship with the entity, such as a customer ora prospective customer. In some instances described herein, the user isan individual who seeks to utilize, operate, or perform one or moreactivities associated with a computer terminal, typically based onsuccessful validation of the user's authentication credentials. In otherembodiments, a user may be a system or an entity performing one or moretasks described herein.

Accordingly, as used herein the term “user device” or “mobile device”may refer to mobile phones, personal computing devices, tabletcomputers, wearable devices, and/or any portable electronic devicecapable of receiving and/or storing data therein.

“Transaction” or “resource transfer” as used herein may refer to anycommunication between a user and a third party merchant or individual totransfer funds for purchasing or selling of a product. A transaction mayrefer to a purchase of goods or services, a return of goods or services,a payment transaction, a credit transaction, or other interactioninvolving a user's account. In the context of a financial institution, atransaction may refer to one or more of: a sale of goods and/orservices, initiating an automated teller machine (ATM) or online bankingsession, an account balance inquiry, a rewards transfer, an accountmoney transfer or withdrawal, opening a bank application on a user'scomputer or mobile device, a user accessing their e-wallet, or any otherinteraction involving the user and/or the user's device that isdetectable by the financial institution. A transaction may include oneor more of the following: renting, selling, and/or leasing goods and/orservices (e.g., groceries, stamps, tickets, DVDs, vending machine items,and the like); making payments to creditors (e.g., paying monthly bills;paying federal, state, and/or local taxes; and the like); sendingremittances; loading money onto stored value cards (SVCs) and/or prepaidcards; donating to charities; and/or the like. “Resource instrument” or“instrument” as defined herein may refer to any instrument that can beutilized to facilitate the transfer of resources (e.g., credit card,debit card, gift card, loyalty card, check, or the like).

The system allows for increased flexibility of resource transfers byenabling a user to establish a virtual link between an account and aresource instrument not originally associated with said account. In someembodiments, the user is able to establish the virtual link from anylocation in real time. A user may not be aware that a primary resourceinstrument is lost or damaged until they attempt to complete atransaction at a third-party merchant location. This system disclosedherein allows the user to rapidly generate a link with a second resourceinstrument in their possession. The user may then complete thetransaction using an account associated with the primary resourceinstrument. There are multiple reasons why a user may choose to use aprimary account for a transaction, such as that account having anadequate balance, desire to obtain rewards offers, wanting to use creditrather than debit, etc. The proposed invention benefits a user bymaintaining the primary choice of account for a transaction whileeliminating the problems caused by a lost, damaged, or misplacedresource instrument.

FIG. 1 illustrates an operating environment 100 for the crosslinkingsystem, in accordance with one embodiment of the present disclosure. Asillustrated, the system environment 100 may comprise a user device 104in operative communication with one or more third party systems 300 viaa network 101. The system environment also includes a user 102, amanaging entity system 400, a crosslinking system 200, a primaryinstitution 500, a secondary institution 600, and/or othersystems/devices not illustrated herein and connected via a network 101.As such, the user device 104 is configured such that the user 102 mayrequest a resource instrument cross link from the managing entity system400 by establishing operative communication channels between the userdevice 104, the managing entity system 400, and/or the crosslinkingsystem 200 via a wireless network 101.

Typically, the crosslinking system 200 is in operative communicationwith the managing entity system 400, the primary institution 500, andthe secondary institution 600 via the network 101, which may be theinternet, an intranet, and/or the like. In FIG. 1, the network 101 mayinclude a local area network (LAN), a wide area network (WAN), a globalarea network (GAN), and/or near field communication (NFC) network. Thenetwork 101 may provide for wireline, wireless, or a combination ofwireline and wireless communication between devices in the network. Insome embodiments, the network 101 includes the Internet. In someembodiments, the network 101 may include a wireless telephone network.Furthermore, the network 101 may comprise wireless communicationnetworks to establish wireless communication channels such as acontactless communication channel and a near field communication (NFC)channel (for example, in the instances where communication channels areestablished between the user device 104 and the managing entity system400). In this regard, the wireless communication channel may furthercomprise near field communication (NFC), communication via radio waves,communication through the internet, communication via electromagneticwaves and the like.

The user device 104 may comprise a mobile communication device, such asa cellular telecommunications device (i.e., a smart phone or mobilephone), a computing device such as a laptop computer, a personal digitalassistant (PDA), a mobile internet accessing device, or other mobiledevice including, but not limited to portable digital assistants (PDAs),pagers, mobile televisions, gaming devices, laptop computers, cameras,video recorders, audio/video player, radio, GPS devices, any combinationof the aforementioned, or the like.

The managing entity system 400 may comprise a communication module andmemory not illustrated, and may be configured to establish operativecommunication channels with a third party system 300 and a user device104 via a network 101. The managing entity may comprise a user datarepository which stores user account data. This data may be used by themanaging entity to facilitate network-based transfers between the userdevice and third party system and may be used to identify resourceinstruments associated with various user accounts. In some embodiments,the managing entity system is in operative communication with thecrosslinking system 200 via a private communication channel. The privatecommunication channel may be via a network 101 or the crosslinkingsystem 200 may be fully integrated within the managing entity system400.

As will be discussed in greater detail in FIG. 4, the managing entitysystem 400 may communicate with the crosslinking system 200 in order tocomplete a resource instrument crosslink request from a user 102. Insome embodiments, the managing entity may utilize the features andfunctions of the crosslinking system to identify active crosslinkrequests and subsequently route transactions to the appropriate entityfor authorization and completion.

FIG. 2 illustrates a block diagram of the crosslinking system 200associated with the operating environment 100, in accordance withembodiments of the present invention. As illustrated in FIG. 2, thecrosslinking system 200 may include a communication device 244, aprocessing device 242, and a memory device 250 having a linkingapplication/module 253, a processing system application 254, aprocessing system datastore 255, and a crosslink database 256 storedtherein. As shown, the processing device 242 is operatively connected toand is configured to control and cause the communication device 244, andthe memory device 250 to perform one or more functions. In someembodiments, the linking module 253 and/or the processing systemapplication 254 comprises computer readable instructions that whenexecuted by the processing device 242 cause the processing device 242 toperform one or more functions and/or transmit control instructions tothe primary institution 500, the secondary institution 600, the managingentity system 400, and/or the communication device 244. It will beunderstood that the linking module 253 and/or the processing systemapplication 254 may be executable to initiate, perform, complete, and/orfacilitate one or more portions of any embodiments described and/orcontemplated herein. The linking module 253 may comprise executableinstructions associated with generation of resource instrumentcrosslinks and routing of associated transactions and may be embodiedwithin the processing system application 254 in some instances. Thecrosslinking system 200 may be owned by, operated by and/or affiliatedwith the same managing entity that owns or operates the managing entitysystem 400. In some embodiments, the crosslinking system 200 is fullyintegrated within the managing entity system 400.

The communication device 244 may generally include a modem, server,transceiver, and/or other devices for communicating with other deviceson the network 101. The network communication device 244 may be acommunication interface having one or more communication devicesconfigured to communicate with one or more other devices on the network101, such as the managing entity system 400, the primary institution500, the secondary institution 600, other processing systems, datasystems, etc.

Additionally, referring to the crosslinking system 200 illustrated inFIG. 2, the processing device 242 may generally refer to a device orcombination of devices having circuitry used for implementing thecommunication and/or logic functions of the crosslinking system 200. Forexample, the processing device 242 may include a control unit, a digitalsignal processor device, a microprocessor device, and variousanalog-to-digital converters, digital-to-analog converters, and othersupport circuits and/or combinations of the foregoing. Control andsignal processing functions of the system 200 may be allocated betweenthese processing devices according to their respective capabilities. Thecomputer processing device or processing device 242 may further includefunctionality to operate one or more software programs based on computerprogram instruction code or computer-executable program code 252thereof, which may be stored in a memory device 250, such as theprocessing system application 254 and the linking module 253. As thephrase is used herein, a processing device may be “configured to”perform a certain function in a variety of ways, including, for example,by having one or more general-purpose circuits perform the function byexecuting particular computer-readable program code or computer-readablecode portions embodied in computer-readable medium, and/or by having oneor more application-specific circuits perform the function. Theprocessing device 242 may be configured to use the network communicationinterface of the communication device 244 to transmit and/or receivedata and/or commands to and/or from the other devices/systems connectedto the network 101.

The memory device 250 within the crosslinking system 200 may generallyrefer to a device or combination of devices that store one or more formsof computer-readable media for storing data and/or computer-executableprogram code/instructions. For example, the memory device 250 mayinclude any computer memory that provides an actual or virtual space totemporarily or permanently store data and/or commands provided to theprocessing device 242 when it carries out its functions describedherein.

It is understood that the servers, systems, and devices described hereinillustrate one embodiment of the invention. It is further understoodthat one or more of the servers, systems, and devices can be combined inother embodiments and still function in the same or similar way as theembodiments described herein.

FIG. 3 is a block diagram illustrating a crosslinking request 310associated with the crosslinking system 200, in accordance with oneembodiment of the present disclosure. The request 310 comprises userinformation 311, primary account data 312, primary resource instrumentdata 313, secondary account data 314, secondary resource instrument data315, and timing information 316. The user information 311 may includeany data identifying a user 102 such as a personal identifier, name,customer number, or the like. The primary account data 312 may compriseinformation identifying an account associated with the user 102, such asaccount type, account number, and/or the like. The primary resourceinstrument data 313 may comprise information identifying a physicalresource instrument associated with the primary account 312, such as acard or check number, a personal identification number (PIN), and/or thelike. The secondary account data 314 may comprise informationidentifying an account other than the primary account associated withthe user 102, such as account type, account number, and/or the like. Thesecondary resource instrument data 315 may comprise informationidentifying a physical resource instrument associated with the secondaryaccount 314, such as a card or check number, a personal identificationnumber (PIN), and/or the like. The timing information 316 may comprisean indication of when the crosslinking system 200 should activate therequest 310. In some embodiments, the timing information 316 may causethe request 310 to be activated immediately. Additionally, oralternatively, the timing information 316 may cause the request 310 tobe activated on a particular date or at a particular future time. Insome embodiments, the timing information 316 may cause the request 310to be deactivated on a particular date or at a particular future time.

FIG. 4 is a high-level process flow diagram illustrating a process usingthe crosslinking system, in accordance with one embodiment of thepresent disclosure. The process begins at block 410, where the systemreceives a crosslink request 310 from the managing entity system 400. Insome embodiments, the managing entity system may transmit a crosslinkrequest to the crosslinking system in response to an initial requestfrom a user 102. The user 102 may make an initial request via a userdevice 104 by sending a call, text, email, instant message, and/or thelike to the managing entity system 400. The process continues in block420, where the system stores the information 311, 312, 313, 314, 315,and 316 in the crosslink database 256. The system then transmits anotification 430 indicating crosslink success to the managing entitysystem 400 via the communication device 244.

The process may then continue to block 440, wherein, after the user 102initiates a transaction with a third party system 300, the systemreceives transaction data from the managing entity system 400. Thetransaction data may include any information gathered from the managingentity system 400 which is required to authorize and complete thetransaction, such as information identifying the user 102, a resourceinstrument used, a transaction amount, information identifying the thirdparty system, and/or the like. The process may then continue to block450, where the crosslinking system compares the transaction data to thecrosslink database 256 to identify any crosslink requests 310 which areboth associated with the user 102 and which are currently active basedon the timing information 316. The system may then compare the resourceinstrument identified in the transaction data to the secondary resourceinstrument data 315 to determine if a match exists 460. If a matchexists, in some embodiments, the process may continue to block 461,where the system transmits the transaction data to the primaryinstitution 500 associated with the primary account 312 of identifiedcrosslink request 310 for transaction authorization and completion.After completion of the transaction by the primary institution 500, thesystem 200 may receive a notification 462 from the primary institutionindicating transaction success.

Additionally, or alternatively, after determining whether a resourceinstrument match exists 460, the process may continue to block 463,wherein the system 200 transmits a message to the secondary institution600 associated with the secondary account 314 of the identifiedcrosslink request 310. The message may include the transaction data,data identifying the primary account 312 of the identified crosslinkrequest 310, and instructions for the secondary institution 600 toforward the transaction data to the primary institution 500 fortransaction authorization and completion. After completion of thetransaction by the primary institution 500, the system 200 may receive anotification 462 from the primary institution 500 or secondaryinstitution 600 indicating transaction success.

As will be appreciated by one of ordinary skill in the art, the presentinvention may be embodied as an apparatus (including, for example, asystem, a machine, a device, a computer program product, and/or thelike), as a method (including, for example, a business process, acomputer-implemented process, and/or the like), or as any combination ofthe foregoing. Accordingly, embodiments of the present invention maytake the form of an entirely software embodiment (including firmware,resident software, micro-code, and the like), an entirely hardwareembodiment, or an embodiment combining software and hardware aspectsthat may generally be referred to herein as a “system.” Furthermore,embodiments of the present invention may take the form of a computerprogram product that includes a computer-readable storage medium havingcomputer-executable program code portions stored therein.

As the phrase is used herein, a processor may be “configured to” performa certain function in a variety of ways, including, for example, byhaving one or more general-purpose circuits perform the function byexecuting particular computer-executable program code embodied incomputer-readable medium, and/or by having one or moreapplication-specific circuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, infrared, electromagnetic, and/orsemiconductor system, apparatus, and/or device. For example, in someembodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EEPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as apropagation signal including computer-executable program code portionsor executable portions embodied therein.

It will also be understood that one or more computer-executable programcode portions or instruction code for carrying out or performing thespecialized operations of the present invention may be required on thespecialized computer include object-oriented, scripted, and/orunscripted programming languages, such as, for example, Java, Perl,Smalltalk, C++, SQL, Python, Objective C, and/or the like. In someembodiments, the one or more computer-executable program code portionsfor carrying out operations of embodiments of the present invention arewritten in conventional procedural programming languages, such as the“C” programming languages and/or similar programming languages. Thecomputer program code may alternatively or additionally be written inone or more multi-paradigm programming languages, such as, for example,F #.

Embodiments of the present invention are described above with referenceto flowcharts and/or block diagrams. It will be understood that steps ofthe processes described herein may be performed in orders different thanthose illustrated in the flowcharts. In other words, the processesrepresented by the blocks of a flowchart may, in some embodiments, be inperformed in an order other that the order illustrated, may be combinedor divided, or may be performed simultaneously. It will also beunderstood that the blocks of the block diagrams illustrated, in someembodiments, merely conceptual delineations between systems and one ormore of the systems illustrated by a block in the block diagrams may becombined or share hardware and/or software with another one or more ofthe systems illustrated by a block in the block diagrams. Likewise, adevice, system, apparatus, and/or the like may be made up of one or moredevices, systems, apparatuses, and/or the like. For example, where aprocessor is illustrated or described herein, the processor may be madeup of a plurality of microprocessors or other processing devices whichmay or may not be coupled to one another. Likewise, where a memory isillustrated or described herein, the memory may be made up of aplurality of memory devices which may or may not be coupled to oneanother.

It will also be understood that the one or more computer-executableprogram code portions may be stored in a transitory or non-transitorycomputer-readable medium (e.g., a memory, and the like) that can directa computer and/or other programmable data processing apparatus tofunction in a particular manner, such that the computer-executableprogram code portions stored in the computer-readable medium produce anarticle of manufacture, including instruction mechanisms which implementthe steps and/or functions specified in the flowchart(s) and/or blockdiagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with operator and/orhuman-implemented steps in order to carry out an embodiment of thepresent invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

What is claimed is:
 1. A system for authorization and use ofcross-linked resource instruments, the system comprising: a memorydevice with computer-readable program code stored thereon; acommunication device; and a processing device operatively coupled to thememory device and the communication device, wherein the processingdevice is configured to execute the computer-readable program code to:receive, from a managing entity, a request for a crosslink, wherein therequest comprises information identifying a requester, informationidentifying a resource instrument, information identifying an accountassociated with the requester and not associated with the resourceinstrument, and information indicating a time at which to activate therequest; store the request in a crosslink database; receive, from themanaging entity, transaction data from a transaction between a user anda third party system, wherein the transaction data comprises at leastinformation identifying the user, information identifying the resourceinstrument used, and a timestamp; identify, based on the informationidentifying the user, a stored request in the crosslink database whereinthe requester matches the user identified in the transaction data andthe request is activated during the time at which the transactionoccurred; determine whether the resource instrument identified in thestored request matches the resource instrument identified in thetransaction data; transmit, based on determining that the resourceinstrument identified in the stored request matches the resourceinstrument identified in the transaction data, the transaction data to aprimary institution system associated with the account identified in thestored request; and receive, from the primary institution system, aconfirmation of transaction authorization and completion.
 2. The systemof claim 1, wherein the processing device is further configured toexecute the computer-readable program code to transmit, to the managingentity and based on the request for the crosslink being stored in thecrosslink database, a notification.
 3. The system of claim 1, whereinthe request for the crosslink from the managing entity is generated bythe managing entity in response to receiving a user request from a userdevice via a network.
 4. The system of claim 1, wherein the informationindicating the time at which to activate the request indicates that therequest is activated immediately.
 5. The system of claim 1, wherein therequest comprises information indicating another time at which todeactivate the request.
 6. The system of claim 1, wherein the requestfor the crosslink further comprises information indicating a secondaryaccount, wherein the secondary account is associated with both therequester and the resource instrument identified in the request.
 7. Thesystem of claim 6, wherein the processing device is further configuredto execute the computer-readable program code to transmit, based ondetermining that the resource instrument identified in the storedrequest matches the resource instrument identified in the transactiondata, a message comprising the transaction data to a secondaryinstitution system associated with the secondary account identified inthe stored request.
 8. The system of claim 7, wherein the messagetransmitted to the secondary institution system further comprisesinformation identifying the primary institution system and instructionsto forward the transaction data to the primary institution system.
 9. Acomputer program product for authorization and use of cross-linkedresource instruments with at least one non-transitory computer-readablemedium having computer-readable program code portions embodied therein,the computer-readable program code portions comprising: an executableportion configured to receive, from a managing entity, a request for acrosslink, wherein the request comprises information identifying arequester, information identifying a resource instrument, informationidentifying an account associated with the requester and not associatedwith the resource instrument, and information indicating a time at whichto activate the request; an executable portion configured to store therequest in a crosslink database; an executable portion configured toreceive, from the managing entity, transaction data from a transactionbetween a user and a third party system, wherein the transaction datacomprises at least information identifying the user, informationidentifying the resource instrument used, and a timestamp; an executableportion configured to identify, based on the information identifying theuser, a stored request in the crosslink database wherein the requestermatches the user identified in the transaction data and the request isactivated during the time at which the transaction occurred; anexecutable portion configured to determine whether the resourceinstrument identified in the stored request matches the resourceinstrument identified in the transaction data; an executable portionconfigured to transmit, based on determining that the resourceinstrument identified in the stored request matches the resourceinstrument identified in the transaction data, the transaction data to aprimary institution system associated with the account identified in thestored request; and an executable portion configured to receive, fromthe primary institution system, a confirmation of transactionauthorization and completion.
 10. The computer program product of claim9, further comprising an executable portion configured to transmit, tothe managing entity and based on the request for the crosslink beingstored in the crosslink database, a notification.
 11. The computerprogram product of claim 10, wherein the request for the crosslink fromthe managing entity is generated by the managing entity in response toreceiving a user request from a user device via a network.
 12. Thecomputer program product of claim 9, wherein the information indicatingthe time at which to activate the request indicates that the request isactivated immediately.
 13. The computer program product of claim 9,wherein the request comprises information indicating another time atwhich to deactivate the request.
 14. The computer program product ofclaim 9, wherein the request for the crosslink further comprisesinformation indicating a secondary account, wherein the secondaryaccount is associated with both the requester and the resourceinstrument identified in the request.
 15. The computer program productof claim 14, wherein the computer-readable program code portions furthercomprise an executable portion configured to transmit, based ondetermining that the resource instrument identified in the storedrequest matches the resource instrument identified in the transactiondata, a message comprising the transaction data to a secondaryinstitution system associated with the secondary account identified inthe stored request.
 16. The computer program product of claim 15,wherein the message transmitted to the secondary institution systemfurther comprises information identifying the primary institution systemand instructions to forward the transaction data to the primaryinstitution system.
 17. A computer-implemented method for authorizationand use of cross-linked resource instruments, the method comprising:providing a computing system comprising a computer processing device anda non-transitory computer readable medium, where the computer readablemedium comprises configured computer program instruction code, such thatwhen said instruction code is operated by said computer processingdevice, said computer processing device performs the followingoperations: receiving, from a managing entity, a request for acrosslink, wherein the request comprises information identifying arequester, information identifying a resource instrument, informationidentifying an account associated with the requester and not associatedwith the resource instrument, and information indicating a time at whichto activate the request; storing the request in a crosslink database;receiving, from the managing entity, transaction data from a transactionbetween a user and a third party system, wherein the transaction datacomprises at least information identifying the user, informationidentifying the resource instrument used, and a timestamp; identifying,based on the information identifying the user, a stored request in thecrosslink database wherein the requester matches the user identified inthe transaction data and the request is activated during the time atwhich the transaction occurred; determining whether the resourceinstrument identified in the stored request matches the resourceinstrument identified in the transaction data; transmitting, based ondetermining that the resource instrument identified in the storedrequest matches the resource instrument identified in the transactiondata, the transaction data to a primary institution system associatedwith the account identified in the stored request; and receiving, fromthe primary institution system, a confirmation of transactionauthorization and completion.
 18. The computer-implemented method ofclaim 17, wherein the request for the crosslink from the managing entityis generated by the managing entity in response to receiving a userrequest from a user device via a network.
 19. The computer-implementedmethod of claim 18, wherein the information indicating the time at whichto activate the request indicates that the request is activatedimmediately, and wherein the request further comprises informationindicating another time at which to deactivate the request.
 20. Thecomputer-implemented method of claim 17, wherein the request for thecrosslink further comprises information indicating a secondary account,wherein the secondary account is associated with both the requester andthe resource instrument identified in the request, and wherein thecomputer processing device transmits, based on determining that theresource instrument identified in the stored request matches theresource instrument identified in the transaction data, a message to asecondary institution system associated with the secondary accountidentified in the stored request, wherein the message comprisesinformation identifying the primary institution system and instructionsto forward the transaction data to the primary institution system.